Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency Pulumi.Kubernetes to v4 #45

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 19, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Pulumi.Kubernetes (source) 3.23.1 -> 4.19.0 age adoption passing confidence

Release Notes

pulumi/pulumi-kubernetes (Pulumi.Kubernetes)

v4.19.0

Changed

v4.18.4

Changed
Fixed

v4.18.3

Fixed

v4.18.2

Fixed

v4.18.1

Added
Changed

v4.18.0

Added
  • The new enableSecretMutable provider configuration option treats changes to
    Secrets as updates instead of replacements (similar to the
    enableConfigMapMutable option).

    The default replacement behavior can be preserved for a particular Secret
    by setting its immutable field to true.
    https://github.com/pulumi/pulumi-kubernetes/issues/22912291)

    Note: These options (enableSecretMutable and enableConfigMapMutable)
    may become the default behavior in a future v5 release of the provider.
    Programs that depend on the replacement of Secrets and ConfigMaps (e.g.
    to trigger updates for downstream dependencies like Deployments) are
    recommended to explicitly specify immutable: true.

  • A warning is now emitted if an object has finalizers which might be blocking
    deletiohttps://github.com/pulumi/pulumi-kubernetes/issues/14181418)

  • EXPERIMENTAL: Generic await logic is now available as an opt-in feature.
    Running a program with PULUMI_K8S_AWAIT_ALL=true will now cause Pulumi to
    await readiness for all resources, including custom resources.

    Generic readiness is determined according to some well-known conventions (like
    the "Ready" condition) as determined by cli-utils.

    Pulumi's current behavior, without this feature enabled, is to assume some
    resources are immediately available, which can cause downstream resources to
    fail.

    Existing readiness logic is unaffected by this setting.
    https://github.com/pulumi/pulumi-kubernetes/issues/29962996)

  • EXPERIMENTAL: The pulumi.com/waitFor annotation was introduced to allow
    for custom readiness checks. This override Pulumi's own await logic for the
    resource (however the pulumi.com/skipAwait annotation still takes
    precedence).

    The value of this annotation can take 3 forms:

    1. A string prefixed with jsonpath= followed by a
      JSONPath
      expression and an optional value.

      The JSONPath expression accepts the same syntax as
      kubectl get -o jsonpath={...}.

      If a value is provided, the resource is considered ready when the
      JSONPath expression evaluates to the same value. For example this
      resource expects its "phase" field to have a value of "Running":

      `pulumi.com/waitFor: "jsonpath={.status.phase}=Running"`
      

      If a value is not provided, the resource will be considered ready when
      any value exists at the given path, similar to kubectl wait --for jsonpath=.... This resource will wait until it has a webhook configured
      with a CA bundle:

      `pulumi.com/waitFor: "jsonpath={.webhooks[*].clientConfig.caBundle}"`
      
    2. A string prefixed with condition= followed by the type of the
      condition and an optional status. This matches the behavior of
      kubectl wait --for=condition=... and will wait until the resource has a
      matching condition. The expected status defaults to "True" if not
      specified.

      `pulumi.com/waitFor: "condition=Synced"`
      
      `pulumi.com/waitFor: "condition=Reconciling=False"`
      
    3. A string containing a JSON array of multiple jsonpath= and
      condition= expressions.

      `pulumi.com/waitFor: '["jsonpath={.foo}", "condition=Bar"]'` 
      
  • Pulumi will now emit logs for any Kubernetes "Warning" Events associated with
    resources being created, updated or deletehttps://github.com/pulumi/pulumi-kubernetes/pull/3135ull/3135/files)

Fixed

v4.17.1

Fixed

v4.17.0

Changed
Fixed

v4.16.0

Added
  • clusterIdentifier configuration can now be used to manually control the
    replacement behavior of a provider resourchttps://github.com/pulumi/pulumi-kubernetes/pull/3068ull/3068)

  • Pod errors now include the pod's last termination state, as well as the pod's
    termination message if availablhttps://github.com/pulumi/pulumi-kubernetes/pull/3091ull/3091)

    The pod's termination message can be helpful in CrashLoopBackOff situations but
    will only be reported if it was correctly configured.

    By default, the pod's termination message is read from
    /dev/termination-log. This location can be configured with
    terminationMessagePath.

    Use terminationMessagePolicy: FallbackToLogsOnError to use the pod's logs
    as its termination message.

  • Documentation is now generated for all languages supported by overlay types.
    https://github.com/pulumi/pulumi-kubernetes/pull/31073107)

Fixed

v4.15.0

Changed
Fixed

v4.14.0

Added
Changed
Fixed

v4.13.1

Added
Changed
Fixed

v4.12.0

Added
Changed
Fixed

v4.11.0

v4.10.0

New Features

A new MLC-based implementation of ConfigGroup and of ConfigFile is now available in the "yaml/v2" package. These resources are
usable in all Pulumi languages, including Pulumi YAML and in the Java Pulumi SDK.

Note that transformations aren't supported in this release (see https://github.com/pulumi/pulumi/issues/12996).

v4.9.1

v4.9.0

v4.8.1

v4.8.0

v4.7.1

  • Fix deployment await logic for accurate rollout detection

v4.7.0

Breaking Changes

In previous versions of the pulumi-kubernetes .NET SDK, the ConfigFile and ConfigGroup component resources inadvertently assigned the wrong parent to the child resource(s).
This would happen when the component resource itself had a parent; the child would be assigned that same parent. This also had the effect of disregarding the component resource's provider in favor of the parent's provider.

For example, here's a before/after look at the component hierarchy:

Before:

├─ pkg:index:MyComponent            parent
│  ├─ kubernetes:core/v1:ConfigMap  cg-options-cg-options-cm-1
│  ├─ kubernetes:yaml:ConfigFile    cg-options-testdata/options/configgroup/manifest.yaml
│  ├─ kubernetes:core/v1:ConfigMap  cg-options-configgroup-cm-1
│  ├─ kubernetes:yaml:ConfigFile    cg-options-testdata/options/configgroup/empty.yaml
│  └─ kubernetes:yaml:ConfigGroup   cg-options

After:

└─ pkg:index:MyComponent                  parent
   └─ kubernetes:yaml:ConfigGroup         cg-options
      ├─ kubernetes:yaml:ConfigFile       cg-options-testdata/options/configgroup/manifest.yaml
      │  └─ kubernetes:core/v1:ConfigMap  cg-options-configgroup-cm-1
      └─ kubernetes:core/v1:ConfigMap     cg-options-cg-options-cm-1

This release addresses this issue and attempts to heal existing stacks using aliases. This is effective at avoiding a replacement except in the case where the child was created with the wrong provider. In this case, Pulumi will suggest a replacement of the child resource(s), such that they use the correct provider.

v4.6.1

v4.6.0

Resources Renamed:
  • #/types/kubernetes:core/v1:ResourceRequirements
    • renamed to: #/types/kubernetes:core/v1:VolumeResourceRequirements
  • #/types/kubernetes:core/v1:ResourceRequirementsPatch
    • renamed to: #/types/kubernetes:core/v1:VolumeResourceRequirementsPatch
New Resources:
  • flowcontrol.apiserver.k8s.io/v1.FlowSchema
  • flowcontrol.apiserver.k8s.io/v1.FlowSchemaList
  • flowcontrol.apiserver.k8s.io/v1.FlowSchemaPatch
  • flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfiguration
  • flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationList
  • flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationPatch
  • networking.k8s.io/v1alpha1.ServiceCIDR
  • networking.k8s.io/v1alpha1.ServiceCIDRList
  • networking.k8s.io/v1alpha1.ServiceCIDRPatch
  • storage.k8s.io/v1alpha1.VolumeAttributesClass
  • storage.k8s.io/v1alpha1.VolumeAttributesClassList
  • storage.k8s.io/v1alpha1.VolumeAttributesClassPatch

v4.5.6

v4.5.5

v4.5.4

v4.5.3

v4.5.2

v4.5.1

v4.5.0

v4.4.0

v4.3.0

v4.2.0

  • Reintroduce switching builds to pyproject.toml; when publishing the package to PyPI both
    source-based and wheel distributions are now published. For most users the installs will now favor
    the wheel distribution, but users invoking pip with --no-binary :all: will continue having
    installs based on the source distribution.
  • Return mapping information for terraform conversions (https://github.com/pulumi/pulumi-kubernetes/pull/2457)
  • feature: added skipUpdateUnreachable flag to proceed with the updates without failing (https://github.com/pulumi/pulumi-kubernetes/pull/2528)

v4.1.1

v4.1.0

v4.0.3

v4.0.2

v4.0.1

v4.0.0

Breaking changes:

Other changes:

v3.30.2

v3.30.1

v3.30.0

v3.29.1

v3.29.0

v3.28.1

v3.28.0

v3.27.1

v3.27.0

v3.26.0

v3.25.0

  • Update Kubernetes to v1.27.0
New resources:
authentication.k8s.io/v1beta1.SelfSubjectReview
authentication.k8s.io/v1beta1.SelfSubjectReviewPatch
certificates.k8s.io/v1alpha1.ClusterTrustBundle
certificates.k8s.io/v1alpha1.ClusterTrustBundleList
certificates.k8s.io/v1alpha1.ClusterTrustBundlePatch
networking.k8s.io/v1alpha1.IPAddress
networking.k8s.io/v1alpha1.IPAddressList
networking.k8s.io/v1alpha1.IPAddressPatch
resource.k8s.io/v1alpha2.PodSchedulingContext
resource.k8s.io/v1alpha2.PodSchedulingContextList
resource.k8s.io/v1alpha2.PodSchedulingContextPatch
resource.k8s.io/v1alpha2.ResourceClaim
resource.k8s.io/v1alpha2.ResourceClaimList
resource.k8s.io/v1alpha2.ResourceClaimPatch
resource.k8s.io/v1alpha2.ResourceClaimTemplate
resource.k8s.io/v1alpha2.ResourceClaimTemplateList
resource.k8s.io/v1alpha2.ResourceClaimTemplatePatch
resource.k8s.io/v1alpha2.ResourceClass
resource.k8s.io/v1alpha2.ResourceClassList
resource.k8s.io/v1alpha2.ResourceClassPatch
Resources moved from v1alpha1 to v1alpha2
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimTemplateList"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClassList"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClassPatch"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimList"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClass"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimTemplate"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimTemplatePatch"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaim"
  • "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimPatch"
Resources moved from v1beta1 to v1
  • "kubernetes:storage.k8s.io/v1beta1:CSIStorageCapacity"
  • "kubernetes:storage.k8s.io/v1beta1:CSIStorageCapacityPatch"
  • "kubernetes:storage.k8s.io/v1beta1:CSIStorageCapacityList"
Resources renamed
  • "kubernetes:resource.k8s.io/v1alpha1:PodSchedulingList"
    • Renamed to kubernetes:resource.k8s.io/v1alpha2:PodSchedulingContextList
  • "kubernetes:resource.k8s.io/v1alpha1:PodSchedulingPatch"
    • Renamed to kubernetes:resource.k8s.io/v1alpha2:PodSchedulingContextPatch
  • "kubernetes:resource.k8s.io/v1alpha1:PodScheduling"
    • Renamed to kubernetes:resource.k8s.io/v1alpha2:PodSchedulingContext
New Features

v3.24.3

v3.24.2

v3.24.1

v3.24.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 3 times, most recently from 3e51f58 to 4841a81 Compare July 21, 2023 18:08
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 4841a81 to 9af1a7c Compare August 16, 2023 05:07
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 9af1a7c to d03cb6a Compare August 24, 2023 02:37
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from d03cb6a to 860bd78 Compare September 14, 2023 20:10
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 860bd78 to 26b279b Compare September 25, 2023 20:04
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 26b279b to 83bbcaf Compare October 12, 2023 21:55
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 3 times, most recently from 12bd6f0 to 92e8f14 Compare October 26, 2023 19:37
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 92e8f14 to 7f4db9c Compare November 1, 2023 01:39
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 7f4db9c to 3bad17c Compare November 9, 2023 00:20
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 3bad17c to 275c732 Compare November 29, 2023 03:51
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from 72e508e to 54c2692 Compare December 15, 2023 03:13
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from 10f1082 to 73fcfe0 Compare January 19, 2024 22:36
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from bca7301 to dec6e93 Compare February 27, 2024 01:31
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from dec6e93 to 42d3e45 Compare March 5, 2024 07:42
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 42d3e45 to 57bd3e0 Compare March 14, 2024 01:29
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from 3ad0234 to d72bb99 Compare April 18, 2024 10:01
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from d72bb99 to 8ab48b1 Compare May 22, 2024 03:53
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 8ab48b1 to d2bb667 Compare June 5, 2024 01:34
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from d2bb667 to e530b7a Compare June 28, 2024 22:33
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from e530b7a to 2a185c3 Compare July 10, 2024 20:04
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from 2ff70e4 to 95365df Compare August 13, 2024 22:23
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 95365df to 8e366c6 Compare August 16, 2024 22:10
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch 2 times, most recently from 9f5c692 to 7883146 Compare September 14, 2024 00:38
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from 7883146 to d70aa02 Compare October 16, 2024 22:22
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from d70aa02 to fded3c7 Compare October 31, 2024 22:59
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from fded3c7 to cb65340 Compare December 6, 2024 00:13
@renovate renovate bot force-pushed the renovate/pulumi.kubernetes-4.x branch from cb65340 to 531ecb6 Compare December 12, 2024 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants